Information processing device, non-transitory computer readable recording medium, and information processing system

ABSTRACT

According to one embodiment, an information processing device includes a nonvolatile memory, assignment unit, and transmission unit. The assignment unit assigns logical address spaces to spaces. Each of the spaces is assigned to at least one write management area included in a nonvolatile memory. The write management area is a unit of an area which manages the number of write. The transmission unit transmits a command for the nonvolatile memory and identification data of a space assigned to a logical address space corresponding to the command.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 16/710,838filed Dec. 11, 2019, which is a continuation of application Ser. No.15/944,191, filed Apr. 3, 2018, which is a continuation of applicationSer. No. 14/656,413, filed Mar. 12, 2015 and claims the benefit of U.S.Provisional Application No. 62/090,690, filed Dec. 11, 2014, the entirecontents of which are incorporated herein by reference.

FIELD

Embodiments described herein relate generally to an informationprocessing device, non-transitory computer readable recording medium,and information processing system.

BACKGROUND

A solid state drive (SSD) includes a nonvolatile semiconductor memoryand has an interface which is similar to that of a hard disk drive(HDD). For example, at the time of data writing, the SSD receives awrite command, logical block addressing (LBA) of a writing destination,and write data from an information processing device, translates the LBAinto physical block addressing (PBA) based on a lookup table (LUT), andwrites the write data to a position indicated by the PBA.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a block diagram showing an example of a structure of aninformation processing system according to a first embodiment;

FIG. 2 is a block diagram showing an example of a relationship betweenLBA spaces, namespaces, address translation tables, garbage collectionunits, and management data;

FIG. 3 is a flowchart showing an example of a process performed by areception unit and a configuration unit according to the firstembodiment;

FIG. 4 is a flow chart showing an example of a process performed by agarbage collection unit and an address translation unit according to thefirst embodiment;

FIG. 5 is a block diagram showing an example of an allocating state ofnamespaces according to the first embodiment;

FIG. 6 is a flow chart showing an example of a process executed by theinformation processing device according to the first embodiment;

FIG. 7 is a block diagram showing an example of a structure of aninformation processing system of a second embodiment;

FIG. 8 is a data structural diagram showing an example of a translationtable according to the second embodiment;

FIG. 9 is a flowchart showing an example of a write process of a memorysystem according to the second embodiment;

FIG. 10 is a flowchart showing an example of a read process of thememory system of the second embodiment;

FIG. 11 is a block diagram showing an example of a structure of aninformation processing system according to a third embodiment; and

FIG. 12 is a perspective view showing a storage system according to thethird embodiment.

DETAILED DESCRIPTION

In general, according to one embodiment, an information processingdevice includes an assignment unit, and transmission unit. Theassignment unit assigns logical address spaces to spaces. Each of thespaces is assigned to at least one write management area of writemanagement areas included in a nonvolatile memory. The write managementarea is a unit of an area which manages the number of write. Thetransmission unit transmits a command for the nonvolatile memory andidentification data of a space assigned to a logical address spacecorresponding to the command.

Embodiments will be described hereinafter with reference to drawings. Ina following description, the same reference numerals denote componentshaving nearly the same functions and arrangements, and a repetitivedescription thereof will be given if necessary. In the followingembodiments, access means both data reading and data writing.

First Embodiment

FIG. 1 is a block diagram showing an example of a structure of aninformation processing system according to the present embodiment.

An information processing system 1 includes an information processingdevice 2 and a memory system 3. The information processing system 1 mayinclude a plurality of information processing device 2. A case where theinformation processing system 1 includes a plurality of informationprocessing device 2 is explained later in a second embodiment.

(Explanation of the Memory System 3)

The memory system 3 is, for example, an SSD, and includes a controller 4and a nonvolatile memory 5. The memory system 3 may be included in theinformation processing device 2, and the information processing device 2and the memory system 3 may be connected through a network in a datacommunicative manner.

In the present embodiment, at least one NAND flash memory is used as thenonvolatile memory 5. However, the present embodiment can be applied tovarious nonvolatile memories including a plurality of write managementareas, and such various nonvolatile memories may be, for example, a NORflash memory, magnetoresistive random access memory (MRAM), phase changerandom access memory (PRAM), resistive random access memory (ReRAM), andferroelectric random access memory (FeRAM). Here, the write managementarea is an area of a unit which manages the number of writes. Thenonvolatile memory 5 may include a three dimensional memory.

For example, the nonvolatile memory 5 includes a plurality of blocks(physical blocks). The plurality of blocks include a plurality of memorycells arranged at crossing points of word lines and bit lines. In thenonvolatile memory 5, data are erased at once block by block. That is, ablock is an area of a unit of data erase. Data write and data read areperformed page by page (word line by word line) in each block. That is,a page is an area of a unit of data write or an area of a unit of dataread.

In the present embodiment, the number of writes is managed block byblock.

The information processing device 2 is a host device of the memorysystem 3. The information processing device 2 sends a configurationcommand C1 which associates the blocks of the nonvolatile memory 5 witha space including at least one block to the memory system 3.

In the following description, the space will be explained as anamespace.

Furthermore, the information processing device 2 sends a write commandC2 together with namespace identification data (NSID) 6, LBA7 whichindicates a writing destination, data size 8 of the write data, andwrite data 9 to the memory system 3.

In the present embodiment, a plurality of namespaces NS₀ to NS_(M) (M isan integer which is 1 or more) are each space which can be obtained fromdividing a plurality of blocks B₀ to B_(N) (N is an integer which is Mor more) included in the nonvolatile memory 5. In the presentembodiment, the namespace NS₀ includes the blocks B₀ to B₂, and thenamespace NS_(M) includes the blocks B_(N-2) to B_(N). The othernamespaces NS₁ to NS_(M-1) are the same as the namespaces NS₀ andNS_(M). Note that the assignment relationship between the namespaces NS₀to NS_(M) and the blocks B₀ to B_(N) is an example, and the number ofthe blocks to be assigned to a single namespace can be arbitrarilychanged. The number of blocks may be different between namespaces.

The controller 4 includes a memory unit 10, buffer memories F₀ to F_(M),and a processor 11.

The memory unit 10 stores address translation tables T₀ to T_(M)corresponding to their respective namespaces NS₀ to NS_(M). For example,the memory unit 10 may be used as a work memory. The memory unit 10 maybe a volatile memory such as dynamic random access memory (DRAM) orstatic random access memory (SRAM), or may be a nonvolatile memory. Thememory unit 10 may be a combination of a volatile memory and anonvolatile memory.

Each of address translation tables T₀ to T_(M) is data associating LBAwith PBA based on the data write with respect to namespaces NS₀ toNS_(M), and may be LUT, for example. Note that a part of or the wholeaddress translation tables T0 to TM may be stored in a different memorysuch as memory 12.

Each of buffer memories F₀ to F_(M) stores the write data until the dataamount becomes suitable based on the data write with respect tonamespaces NS₀ to NS_(M).

The processor 11 includes a memory 12, reception unit 13, configurationunit 14, address translation unit 15, write unit 16, and garbagecollection unit G₀ to G_(M).

The memory 12 stores a program 17 and management data 18. In the presentembodiment, the memory 12 is included in the processor 11; however, itmay be provided outside the processor 11. The memory 12 is, for example,a nonvolatile memory. Note that a part of or the whole program 17 andmanagement data 18 may be stored in a different memory such as thememory unit 10.

The program 17 is, for example, a firmware. The processor 11 executesthe program 17 to function as the reception unit 13, configuration unit14, address translation unit 15, write unit 16, and garbage collectionunits G₀ to G_(M).

The management data 18 indicates a relationship between the namespacesNS₀ to NS_(M) and the blocks B₀ to B_(N). Referring to the managementdata 18, which block is in which namespace can be determined.

The reception unit 13 receives, from the information processing device2, the configuration command C1 to associate each block with eachnamespace in the nonvolatile memory 5. Furthermore, the reception unit13 receives, from the information processing device 2, the write commandC2, NSID6, LBA7, data size 8, and data 9.

In the following description, a case where the write commend C2 is withthe NSID6 which represents the namespace NS₀ is explained for the sakeof simplification. However, the write command C2 can be with the NSIDwhich represents the other namespaces NS₁ to NS_(M).

When the reception unit 13 receives the configuration command C1 of thenamespace, the configuration unit 14 assigns the blocks B₀ to B_(N) tothe namespaces NS₀ to NS_(M) to generate the management data 18 andstores the management data 18 in the memory 12. The assignment of theblocks B₀ to B_(N) to the namespaces NS₀ to NS_(M) may be performed bythe configuration unit 14 observing data storage conditions of thenamespaces NS₀ to NS_(M) in such a manner that the data capacities,access frequencies, write frequencies, the numbers of accesses, thenumbers of writes, or data storage ratios are set to the same levelbetween the namespaces NS₀ to NS_(M). Or, the assignment may beperformed based on an instruction from the information processing device2, or an instruction from the manager of the memory system 3.

The data capacity here is a writable data size, the access frequency orthe write frequency is the number of accesses or the number of writesper unit time, and the data storage ratio is a value which indicates aratio of an area size which the data is already stored with respect toan area size.

Furthermore, the configuration unit 14 transfers an empty block in whichno data is stored from a namespace categorized as pre-garbage collectionto the other namespace based on the garbage collection result executedfor each of the namespaces NS₀ to NS_(M), and updates the managementdata 18. Thus, the wear leveling can be performed between the namespacesNS₀ to NS_(M). The assignment change between the namespaces NS₀ toNS_(M) and the blocks B₀ to B_(N) may be performed by the configurationunit 14 observing the data storage conditions of the namespaces NS₀ toNS_(M) based on an observation result as in the time of generation ofthe management data 18. Or, the assignment change may be performed basedon an instruction from the information processing device 2 or aninstruction from the manager of the memory system 3. For example, thechange of the namespaces NS₀ to NS_(M) are performed to convert theempty block of the namespace with lower data capacity, lower accessfrequency, lower number of access, or lower data storage ratio to thenamespace with higher data capacity, higher access frequency, highernumber of access, or higher data storage ratio.

Furthermore, the configuration unit 14 sets provisioning areas P₀ toP_(M) which are not normally used for each of the namespaces NS₀ toNS_(M) in the nonvolatile memory 5 based on the configuration command C1for over provisioning. The setting of the provisioning areas P₀ to P_(M)may be performed by the configuration unit 14 based on the data capacityof each of the namespaces NS₀ to NS_(M). Or, the setting may beperformed based on an instruction from the information processing device2, or an instruction from the manager of the memory system 3.

In the present embodiment, the provisioning areas P₀ to P_(M) aresecured in the nonvolatile memory 5; however, they may be secured in anyother memory in the memory system 3. For example, the provisioning areasP₀ to P_(M) may be secured in a memory such as DRAM or SRAM.

When the reception unit 13 receives the write command C2, the addresstranslation unit 15 executes associating to translate the LBA7 with thewrite command C2 into the PBA for the address translation table T₀corresponding to the namespace NS₀ which indicates the NSID 6 with thewrite command C2.

In the present embodiment, the address translation unit 15 is achievedby the processor 11; however, the address translation unit 15 may bestructured separately from the processor 11.

Furthermore, the address translation unit 15 performs the addresstranslation based on the address translation tables T₀ to T_(M);however, the address translation may be performed by a key-value typeretrieval. For example, the LBA is set as a key and the PBA is set as avalue for achieving the address translation by key-value type retrieval.

The write unit 16 writes the write data 9 in a position indicated by thePBA obtained from the address translation unit 15. In the presentembodiment, the write unit 16 stores the write data 9 in the buffermemory F₀ corresponding to the namespace NS₀ indicated by the NSID6 withthe write command C2. Then, the write unit 16 writes the data of thebuffer memory F₀ to a position indicated by the PBA when the buffermemory F₀ reaches the data amount suitable for the namespace NS₀.

The garbage collection units G₀ to G_(M) correspond to the namespacesNS₀ to NS_(M) and execute the garbage collection in each of thenamespaces NS₀ to NS_(M). The garbage collection is a process to releasean unnecessary memory area or a process to secure a continuous availablememory area by collecting data written in a memory area with gaps. Thegarbage collection units G₀ to G_(M) may be configured to executegarbage collections in parallel, or consecutively.

The garbage collection is explained in detail using the garbagecollection unit G₀ as an example selected from the garbage collectionunit G₀ to G_(M). The garbage collection unit G₀ first selects theblocks B₀ to B₂ corresponding to the namespace NS₀ based on themanagement data 18. Then, the garbage collection unit G₀ performs thegarbage collection with respect to the selected blocks B₀ to B₂. Then,based on a result of the garbage collection performed by the garbagecollection unit G₀, the address translation unit 15 updates the addresstranslation table T₀.

Note that, in the present embodiment, the LBA and the PBA are associatedwith each other in the address translation tables T₀ to T_(M) and theblock identifiable by the PBA and the NSID are associated with eachother in the management data 18. Therefore, when LBA is a unique addresswithout redundant other LBA and the management data 18 is generated, thenamespace NS₀ which is a writing destination can be specified from theLBA 7 attached to the write command C2 at the processor 11 side.Therefore, after the generation of the management data 18 withoutredundant LBA 7, attaching the NSID 6 to the write command C2 can beomitted, and the NSID 6 may be acquired at the processor 11 side basedon the LBA 7, address translation tables T₀ to T_(M), and managementdata 18.

FIG. 2 is a block diagram showing an example of a relationship betweenLBA spaces, the namespaces NS₀ to NS_(M), the address translation tablesT₀ to T_(M), the garbage collection units G₀ to G_(M), and themanagement data 18.

LBA spaces A₀ to A_(M) of the information processing device 2 areassigned to the namespaces NS₀ to NS_(M), respectively.

The LBA space A₀ includes logical addresses 0 to E₀. The LBA space A₁includes logical addresses 0 to E₁. The LBA space A_(M) includes logicaladdresses 0 to E_(M). The other LBA spaces A₂ to A_(M-1) include aplurality of logical addresses similarly.

In the following description, the LBA space A₀ and the namespace NS₀assigned to the LBA space A₀ are explained representatively for the sakeof simplification. However, the other LBA spaces A₁ to A_(M) andnamespaces NS₁ to NS_(M) are structured the same.

When writing the data of the LBA space A₀ to the nonvolatile memory 5,the information processing device 2 sends the write command C2, NSID 6indicating the namespace NS₀ corresponding to the LBA space A₀, LBA 7within LBA space A₀, data size 8, and write data 9 corresponding to theLBA 7 to the memory system 3.

The management data 18 associates the namespace NS₀ with the blocks B₀to B₂.

The garbage collection unit G₀ performs the garbage collection withrespect to the blocks B₀ to B₂ included in the namespace NS₀corresponding to the garbage collection unit G₀ based on the managementdata 18.

As a result of the garbage collection, data arrangement will be changedwithin the blocks B₀ to B₂. Therefore, the garbage collection unit G₀instructs the address translation unit 15 which is omitted in FIG. 2 toperform the update of address translation table T₀. The addresstranslation unit 15 updates the address translation table T₀corresponding to the namespace NS₀ to match the data arrangement afterthe garbage collection.

FIG. 3 is a flowchart showing an example of a process performed by thereception unit 13 and the configuration unit 14 according to the presentembodiment.

In step S301, the reception unit 13 receives the configuration commandC1 of the namespaces NS₀ to NS_(M). In step S302, the configuration unit14 assigns the blocks B₀ to B_(N) of the nonvolatile memory 5 to thenamespaces NS₀ to NS_(M) and generates the management data 18.

In step S303, the configuration unit 14 stores the management data 18 inthe memory 12.

FIG. 4 is a flow chart showing an example of a process performed by thegarbage collection unit G₀ and the address translation unit 15 accordingto the present embodiment. Note that the same process is executed in theother garbage collection units G₁ to G_(M). The process shown in FIG. 4may be performed based on an instruction from the information processingdevice 2, for example. Or, the process may be performed based on aninstruction from the manager of the memory system 3. Furthermore, thegarbage collection unit G₀ may execute the process of FIG. 4 voluntarilyby, for example, observing the data storage condition of the namespaceNS₀ of the garbage collection target and determining the start of thegarbage collection appropriately. More specifically, the garbagecollection unit G₀ executes the garbage collection with respect to thenamespace NS₀ when the number of empty blocks within the namespace NS₀is a predetermined number or less, or when a ratio of empty blocks tothe whole blocks within the namespace NS₀ is a predetermined value orless.

In step S401, the garbage collection unit G₀ selects the blocks B₀ to B₂corresponding to the namespace NS₀ which is the garbage collectiontarget based on the management data 18.

In step S402, the garbage collection unit G₀ executes the garbagecollection with respect to the blocks B₀ to B₂ within the selectednamespace NS₀.

In step S403, the address translation unit 15 updates the addresstranslation table T₀ corresponding to the namespace NS₀ which is thegarbage collection target based on the conditions of the blocks B₀ to B₂after the garbage collection.

In the present embodiment explained as above, a predetermined blockamount or a block amount set by the information processing device 2 canbe assigned to each of the namespaces NS₀ to NS_(M), and the datacorresponding to the namespaces NS₀ to NS_(M) can be written to theblocks B₀ to B_(M) assigned to the namespaces NS₀ to NS_(M), anddifferent data amounts can be set to the namespaces NS₀ to NS_(M).

In the present embodiment, the garbage collection can be performed ineach of the namespaces NS₀ to NS_(M) independently and efficiently.

In the present embodiment, as a result of the garbage collection, theempty block which do not store data can be transferred from thenamespace before the garbage collection to the other namespace, and theempty block can be secured within the other namespace. Therefore, thenamespace to be assigned to the block can be changed, the wear levelingcan be performed between the namespaces NS₀ to NS_(M), and the life ofthe nonvolatile memory 5 can be prolonged.

In the present embodiment, the provisioning areas P₀ to P_(M) havingdifferent data amounts can be set in each of the namespaces NS₀ toNS_(M), and the over provisioning can be achieved in each of thenamespaces NS₀ to NS_(M). Thus, the write speed can be accelerated andperformance can be maintained, and consequently, the reliability can beimproved.

In the present embodiment, the address translation tables T₀ to T_(M)are managed for each of the namespaces NS₀ to NS_(M), and the addresstranslation and changing of the relationship between the LBA and PBA canbe performed efficiently in each of the namespaces NS₀ to NS_(M).

In the present embodiment, if the address translation is performed bythe key-value type retrieval, even the data volume of the nonvolatilememory 5 is large, the address translation can be performed efficiently.

In the present embodiment, highly sophisticated memory management can beachieved in each of the namespaces NS₀ to NS_(M), the life of thenonvolatile memory 5 can be prolonged, the production costs can bereduced, and write/read processes to/from the nonvolatile memory 5divided by the namespaces NS₀ to NS_(M) can be rapid.

(Explanation of Information Processing Device 2)

The information processing device 2 includes a memory 21 and a processor22.

In the information processing device 2, various programs, includingapplication programs and operating systems, (hereinafter referred to asan object or objects) and various kinds of data can be identified byobject identification data (hereinafter referred to as an object ID orobject IDs).

The information processing device 2 assigns LBA spaces A₀ to A_(M) toobjects, and manages LBA spaces A₀ to A_(M) assigned to each of theobjects identified by their respective object IDs.

The memory 21 is, for example, a nonvolatile memory for storing aprogram 23.

The processor 22 executes the program 23 stored in the memory 21 tofunction as a frequency calculation unit 24, an assignment unit 25 and atransmission unit 26.

The frequency calculation unit 24 calculates the write frequency foreach of the LBA spaces corresponding to each of the objects.

The assignment unit 25 assigns the LBA spaces A₀ to A_(M) to thenamespaces NS₀ to NS_(M) based on the write frequency for each of theLBA spaces corresponding to each of the objects.

The transmission unit 26 generates the configuration command C1 based onan assignment result of the assignment unit 25, and transmits theconfiguration command C1 to the memory system 3.

The transmission unit 26 furthermore generates the write command C2based on the assignment result of the assignment unit 25, and transmitsthe write command C2, the NSID 6 which represents the namespace NS₀assigned to an LBA space of an object transmitting the write command C2,the data size 8 and the write data 9 to the memory system 3.

FIG. 5 is a block diagram showing an example of an allocating state ofnamespaces according to the present embodiment.

FIG. 5 illustrates a state in which the LBA spaces of the objects areassigned to four namespaces NS₀ to NS₃. However, the number of thenamespaces may be two or more.

The write frequencies for the LBA spaces of the objects are assigned toany one of the write frequency groups. FIG. 5 illustrates a case inwhich six write frequency groups L₀ to L₅ are used. Write frequencygroups L₀ to L₅ are successively designated as follows from high to lowin write frequencies: the write frequency group L₀ is designated“Extremely Hot”; the write frequency group L₁, “Hot”; the writefrequency group L₂, “Warm”; the write frequency group L₃, “Cool”; thewrite frequency group L₄, “Cold”; and the write frequency group L₅,“Extremely Cold”.

The write frequency groups L₀ to L₅ are assigned to the namespaces NS₀to NS₃ based on both their respective characteristic features and theirrespective object IDs.

For example, the write frequency groups L₀ to L₅ are assigned to thenamespaces NS₀ to NS₃ in such a manner that the write frequency groupshaving different characteristic features are included in the same namespace.

For example, the write frequency group L₀ is extremely high in writefrequency, which means that extra regions must be secured plentifully.Therefore, the write frequency group L₀ is assigned to the name spacesNS₀ to NS₃. This arrangement makes it possible to use extra regionsefficiently.

For example, the write frequency group L₅, which is extremely low inwrite frequency, is dividedly assigned to the namespaces NS₂ and NS₃.The divisional assignment of the write frequency group L₅ to thenamespaces NS₂ and NS₃ improves efficiency of the garbage collection.

For example, the write frequency group L₁, which is high in writefrequency, is assigned to the namespaces NS₀ or NS₃ on an object basis,and the LBA space of one object is assigned to one namespace NS₀ or NS₃,so that the garbage collection will be independently executed on anobject basis such as on a user application basis. Therefore, when thegarbage collection is executed for a certain user application, theperformance of the other user application is prevented fromdeteriorating.

FIG. 6 is a flowchart showing an example of a process executed by theinformation processing device 2 according to the present embodiment.

In Step S601, the frequency calculation unit 24 calculates the writefrequency for each of the LBA spaces corresponding to each of theobjects.

In Step S602, the assignment unit 25 assigns the LBA space for each ofthe objects to any one of write frequency groups L₀ to L₅ based on thewrite frequency corresponding to the LBA spaces for each of the objects.

In Step S603, the assignment unit 25 assigns each of the LBA spaces toat least one of namespaces NS₀ to NS_(M) based on each object ID andwrite frequency groups L₀ to L₅.

In Step S604, the transmission unit 26 transmits the write command C2,the NSID 6 which represents the assignment result of the namespaces NS₀to NS_(M), the LBA 7, the data size 8 and the write data 9 to the memorysystem 3.

In the present embodiment explained above, the LBA spaces A₀ to A_(M)for each of the objects are assigned to the namespaces NS₀ to NS_(M)based on the write frequency for each of the LBA spaces corresponding toeach of the objects. Therefore, the memory system 3 will be improved inservice quality and device performance, prolonged in lifetime, andappropriate in setting.

For example, the present embodiment makes it possible to adjust thewrite frequency and the number of writes for each of namespaces NS₀ toNS₃ by assigning different LBA spaces having characteristic features toone of the namespaces.

For example, in the present embodiment, an LBA space being extremelyhigh in write frequency can be assigned to a plurality of namespaces,which makes it possible to secure extra regions plentifully.

For example, an LBA space being extremely low in write frequency can beassigned to a plurality of namespaces in the present embodiment, whichmakes it possible to make garbage collection efficient.

For example, in the present embodiment, an LBA space of an object beinghigh in write frequency is assigned to one of the namespaces. Therefore,when the garbage collection is executed for a certain user application,the performance of the other user application is prevented fromdeteriorating.

In the present embodiment, both the assignment of the LBA spaces A₀ toA_(M) and the assignment of the name spaces NS₀ to NS_(M) are executedbased on write frequencies. Instead, however, other information such asa combination of the numbers of writes, write frequencies and readfrequencies may be used to execute both the assignment of the LBA spacesA₀ to A_(M) and the assignment of the namespaces NS₀ to NS_(M).

Furthermore, it is possible to cause the assignment unit 25 respectivelyassign the LBA spaces A₀ to A_(M) to the namespaces NS₀ to NS_(M) basedon the user setting.

In the present embodiment, a compaction unit of each of the namespacesNS₀ to NS_(M) may be provided instead of or together with garbagecollection units G₀ to G_(M). The compaction unit corresponding to eachof namespaces NS₀ to NS_(M) executes compaction with respect to each ofthe namespaces NS₀ to NS_(M) based on the management data 18.

In the present embodiment, the communication of configuration command C1between, for example, the information processing device 2 and the memorysystem 3 may be omitted. For example, the address translation unit 15may include a part of or the whole functions of the configuration unit14. For example, the address translation unit 15 may generate themanagement data 18 and address translation tables T₀ to T_(M) of thenamespaces NS0 to NS_(M) by associating the NSID 6 and LBA 7 added tothe write command C2 with the PBA corresponding to the LBA 7. Themanagement data 18 and the address translation tables T₀ to T_(M) may becoupled or divided arbitrarily. The structure in which the communicationof the configuration command C1 is omitted and the address translationunit 15 includes a part of or the whole functions of the configurationunit 14 is explained in detail in the following second embodiment.

Second Embodiment

In the present embodiment, explained is an information processing systemin which a memory system writes write data from a plurality ofinformation processing devices and sends the read data to theinformation processing devices.

FIG. 7 is a block diagram showing an example of a structure of aninformation processing system of the present embodiment.

An information processing system 1A includes a plurality of informationprocessing devices D₀ to D_(M) and a memory system 3A. Each of theinformation processing devices D₀ to D_(M) functions similarly to theinformation processing device 2. The memory system 3A differs from theabove memory system 3 mainly because it includes a translation table(translation data) 20 instead of the address translation tables T₀ toT_(M) and management data 18, it transmits/receives data, information,signal, and command to/from the information processing devices D₀ toD_(M), and the address translation unit 15 functions as theconfiguration unit 14. In the present embodiment, differences from thefirst embodiment are explained, and the same explanation orsubstantially the same explanation may be omitted or simplified.

The memory system 3A is included in, for example, a cloud computingsystem. In the present embodiment, a case where the memory system 3A isshared with the information processing devices D₀ to D_(M) isexemplified; however, it may be shared with a plurality of users. Atleast one of the information processing devices D₀ to D_(M) may be avirtual machine.

In the present embodiment, NSID added to a command is used as an accesskey to namespaces.

In the present embodiment, the information processing devices D₀ toD_(M) have access rights to their corresponding namespaces NS₀ toNS_(M). However, only a single information processing device may haveaccess rights to one or more namespaces, or a plurality of informationprocessing devices may have an access right to a common namespace.

Each of the information processing devices D₀ to D_(M) transfers,together with the write command C2, an NSID 6W indicative of itscorresponding write destination space, LBA 7W indicative of the writedestination, data size 8, and write data 9W to the memory system 3A.

Each of the information processing devices D₀ to D_(M) transfers,together with a read command C3, an NSID 6R indicative of itscorresponding read destination space, and LBA 7R indicative of the readdestination to the memory system 3A.

Each of the information processing devices D₀ to D_(M) receives readdata 9R corresponding to the read command C3 or information indicativeof a read error from the memory system 3A.

The memory system 3A includes a controller 4A and the nonvolatile memory5.

The controller 4A includes an interface unit 19, memory unit 10, buffermemory F₀ to F_(M), and processor 11. In the present embodiment, thenumber of processor 11 in the controller 4A can be changed optionally tobe one or more.

The interface unit 19 transmits/receives data, information, signal, andcommand to/from external devices such as the information processingdevices D₀ to D_(M).

The memory unit 10 stores a translation table 20. A part of or the wholetranslation table 20 may be stored in a different memory such as thememory 12.

The translation table 20 is data which associates the LBA, PBA, and NSIDwith each other. The translation table 20 is explained later withreference to FIG. 8.

The buffer memories F₀ to F_(M) are used for write buffer memories andread buffer memories with respect to namespaces NS₀ to NS_(M).

The processor 11 includes the memory 12 storing the program 17,reception unit 13, address translation unit 15, write unit 16, read unit21, and garbage collection units G₀ to G_(M). When the program 17 isexecuted, the processor 11 functions as the reception unit 13, addresstranslation unit 15, write unit 16, read unit 21, and garbage collectionunits G₀ to G_(M).

The reception unit 13 receives, at the time of data write, the writecommand C2, NSID 6W, LBA 7W, data size 8, and write data 9W from theinformation processing devices D₀ to D_(M) through the interface unit19.

The reception unit 13 receives, at the time of data read, the readcommand C3, NSID 6R, and LBA 7R from the information processing devicesD₀ to D_(M) through the interface unit 19.

When the reception unit 13 receives the write command C2, based on theLBA 7W and NSID 6W added to the write command C2, the addresstranslation unit 15 determines the PBA of the write destination in thenamespace indicated by the NSID 6W. The address translation unit 15 thenupdates the translation table 20 associating the LBA 7W, NSID 6W, anddetermined PBA with each other.

When the read command C3 is received by the reception unit 13, based onthe LBA 7R and NSID 6R added to the read command C3, and the translationtable 20, the address translation unit 15 determines the PBA of the readdestination indicated by the NSID 6R.

The write unit 16 writes the write data 9W at a position indicated bythe PBA corresponding to the namespace indicated by the NSID 6W via abuffer memory corresponding to the namespace indicated by the NSID 6W.

The read unit 21 reads the read data 9R from the position indicated bythe PBA corresponding to the namespace indicated by NSID 6R via thebuffer memory corresponding to the namespace indicated by NSID 6R. Then,the read unit 21 sends the read data 9R to the information processingdevice issuing the read commend C3 via the interface unit 19.

In the present embodiment, the garbage collection units G₀ to G_(M)execute garbage collection of each of the namespaces NS₀ to NS_(M) basedon the translation table 20.

FIG. 8 is a data structural diagram showing an example of thetranslation table 20 according to the present embodiment.

The translation table 20 manages the LBA, PBA, and NSID with each other.For example, the translation table 20 associates the LBA 200, PBA 300,and NS₀ with each other. For example, the translation table 20associates the LBA 201, PBA 301, and NS₀ with each other. For example,the translation table 20 associates the LBA 200, PBA 399, and NSM witheach other.

The address translation unit 15 determines the PBA such that the PBA 300associated with the LBA 200 and the NSID indicative of the namespace NS₀and PBA 399 associated with the LBA 200 and the NSID indicative of thenamespace NS_(M) differ from each other.

Thus, the address translation unit 15 can select PBA 300 when the NSIDreceived with the LBA 200 indicates the namespace NS₀ and select PBA 399when the NSID received with the LBA 200 indicates the namespace NS_(M).

Therefore, even if the same logical address is used between a pluralityof information processing devices D₀ to D_(M), the memory system 3A canbe shared with the information processing devices D₀ to D_(M).

FIG. 9 is a flowchart showing an example of a write process of thememory system 3A according to the present embodiment.

As to FIG. 9, the explanation thereof is presented given that the writecommand C2 is issued from the information processing device D₀ amongstthe information processing devices D₀ to D_(M), and the NSID 6W whichindicates the namespace NS₀ is added to the write command C2. However,the process is performed similarly when the write commend C2 is issuedfrom any of the information processing devices D₁ to D_(M). Furthermore,the process is performed similarly when the NSID 6W which indicates anyof the other namespaces NS₁ to NS_(M) is added to the write command C2.

In step S901, the reception unit 13 receives the write command C2, NSID6W, LBA 7W, data size 8, and write data 9W from the informationprocessing device D₀ via the interface unit 19.

In step S902, when the write command C2 is received by the receptionunit 13, based on the LBA 7W and NSID 6W added to the write command C2,the address translation unit 15 determines the PBA of a writedestination in the namespace NS₀ indicated by the NSID 6W.

In step S903, the address translation unit 15 updates the translationtable 20 associating the LBA 7W, NSID 6W, determined PBA with eachother.

In step S904, the write unit 16 writes the write data 9W at a positionindicated by the PBA corresponding to the namespace NS₀ indicated by theNSID 6W via the buffer memory F₀ corresponding to the namespace NS₀indicated by the NSID 6W.

FIG. 10 is a flowchart showing an example of a read process of thememory system 3A according to the present embodiment.

As to FIG. 10, the explanation is presented given that the read commandC3 is issued from information processing device DM amongst theinformation processing devices D₀ to D_(M), and the NSID 6R whichindicates the namespace NS_(M) is added to the read command C3. However,the process is performed similarly when the read commend C3 is issuedfrom any of the information processing devices D₁ to D_(M-1).Furthermore, the process is performed similarly when the NSID 6R whichindicates any of the other namespaces NS₁ to NS_(M-1) is added to theread command C3.

In step S1001, the reception unit 13 receives the read command C3, NSID6R, and LBA 7R from the information processing device D_(M) via theinterface unit 19.

In step S1002, when the read command C3 is received by the receptionunit 13, based on the LBA 7R and NSID 6R added to the read command C3,and translation table 20, the address translation unit 15 determines thePBA of a read destination.

In step S1003, the read unit 21 reads the read data 9R from the positionindicated by PBA corresponding to the namespace NS_(M) indicated by NSID6R via the buffer memory F_(M) corresponding to the namespace NS_(M)indicated by NSID 6R, and sends the read data 9R to the informationprocessing devices D_(M) issuing the read command C3 via the interfaceunit 19.

In the present embodiment described above, the nonvolatile memory 5 isdivided into a plurality of the namespaces NS₀ to NS_(M). Theinformation processing devices D₀ to D_(M) can access the namespaceswhose access rights are granted thereto. Consequently, data security canbe improved.

The controller 4A of the memory system 3A controls the namespaces NS₀ toNS_(M) independently space by space. Therefore, conditions of use ofeach of the namespaces NS₀ to NS_(M) may be difference.

The memory system 3A associates the LBA, PBA, and NSID with each other,and thus, even if the same LBA sent from a plurality of independentinformation processing devices is received, the data can bedistinguished based on the NSID.

In each of the above embodiments, data in a table format can beimplemented as a different data structure such as a list format.

Third Embodiment

In the present embodiment, the information processing systems 1 and 1Aexplained in the first and second embodiments are further explained indetail.

FIG. 11 is a block diagram showing of an example of a detail structureof the information processing system 1 according to the presentembodiment.

In FIG. 11, the information processing system 1B includes an informationprocessing device 2B and a memory system 3B. The information processingsystem 1B may include a plurality of information processing devices asin the second embodiment. That is, the information processing devices 2and D0 to DM of the first and second embodiments correspond to theinformation processing devices 2B.

The memory systems 3 and 3A according to the first and secondembodiments correspond to the memory system 3B.

the processor 11 of the first and second embodiments corresponds to CPU43F and 43B.

The address translation tables T₀ to T_(M) according to the firstembodiment and the translation table 20 of the second embodimentcorrespond to a LUT 45.

The memory unit 10 of the first and second embodiments corresponds to aDRAM 47.

The interface unit 19 according to the second embodiment corresponds toa host interface 41 and a host interface controller 42.

The buffer memories F₀ to F_(M) of the first and second embodimentscorrespond to a write buffer WB and read buffer RB.

The information processing device 2B functions as a host device.

The controller 4 includes a front end 4F and a back end 4B.

The front end (host communication unit) 4F includes a host interface 41,host interface controller 42, encode/decode unit 44, and CPU 43F.

The host interface 41 communicates with the information processingdevice 2B to exchange requests (write command, read command, erasecommand), LBA, and data.

The host interface controller (control unit) 42 controls thecommunication of the host interface 41 based on the control of the CPU43F.

The encode/decode unit (advanced encryption standard (AES)) 44 encodesthe write data (plaintext) transmitted from the host interfacecontroller 42 in a data write operation. The encode/decode unit 44decodes encoded read data transmitted from the read buffer RB of theback end 4B in a data read operation. Note that the transmission of thewrite data and read data can be performed without using theencode/decode unit 44 as occasion demands.

The CPU 43F controls the above components 41, 42, and 44 of the frontend 4F to control the whole function of the front end 4F.

The back end (memory communication unit) 4B includes a write buffer WB,read buffer RB, LUT unit 45, DDRC 46, DRAM 47, DMAC 48, ECC 49,randomizer RZ, NANDC 50, and CPU 43B.

The write buffer (write data transfer unit) WB stores the write datatransmitted from the information processing device 2B temporarily.Specifically, the write buffer WB temporarily stores the write datauntil it reaches to a predetermined data size suitable for thenonvolatile memory 5.

The read buffer (read data transfer unit) RB stores the read data readfrom the nonvolatile memory 5 temporarily. Specifically, the read bufferRB rearranges the read data to be the order suitable for the informationprocessing device 2B (the order of the logical address LBA designated bythe information processing device 2B).

The LUT 45 is a data to translate the logical address LBA into apredetermined physical address PBA.

The DDRC 46 controls double data rate (DDR) in the DRAM 47.

The DRAM 47 is a nonvolatile memory which stores, for example, the LUT45.

The direct memory access controller (DMAC) 48 transfers the write dataand the read data through an internal bus IB. In FIG. 11, only a singleDMAC 48 is shown; however, the controller 4 may include two or moreDMACs 48. The DMAC 48 may be set in various positions inside thecontroller 4.

The ECC (error correction unit) 49 adds an error correction code (ECC)to the write data transmitted from the write buffer WB. When the readdata is transmitted to the read buffer RB, the ECC 49, if necessary,corrects the read data read from the nonvolatile memory 5 using theadded ECC.

The randomizer RZ (or scrambler) disperses the write data in such amanner that the write data are not biased in a certain page or in a wordline direction of the nonvolatile memory 5 in the data write operation.By dispersing the write data in this manner, the number of write can bestandardized and the cell life of the memory cell MC of the nonvolatilememory 5 can be prolonged. Therefore, the reliability of the nonvolatilememory 5 can be improved. Furthermore, the read data read from thenonvolatile memory 5 passes through the randomizer RZ in the data readoperation.

The NAND controller (NANDC) 50 uses a plurality of channels (fourchannels CH0 to CH3 are shown in the Figure) to access the nonvolatilememory 5 in parallel in order to satisfy a demand for a certain speed.

The CPU 43B controls each component above (45 to 50, and RZ) of the backend 4B to control the whole function of the back end 4B.

Note that the structure of the controller 4 shown in FIG. 11 is anexample and no limitation is intended thereby.

FIG. 12 is a perspective view showing a storage system according to thepresent embodiment.

The storage system 100 includes the memory system 3B as an SSD.

The memory system 3B is, for example, a relatively small module of whichexternal size will be approximately 20 mm×30 mm. Note that the size andscale of the memory system 3B is not limited thereto and may be changedinto various sizes arbitrarily.

Furthermore, the memory system 3B may be applicable to the informationprocessing device 2B as a server used in a data center or a cloudcomputing system employed in a company (enterprise) or the like. Thus,the memory system 3B may be an enterprise SSD (eSSD).

The memory system 3B includes a plurality of connectors (for example,slots) 30 opening upwardly, for example. Each connector 30 is a serialattached SCSI (SAS) connector or the like. With the SAS connector, ahigh speed mutual communication can be established between theinformation processing device 2B and each memory system 3B via a dualport of 6 Gbps. Note that, the connector 30 may be a PCI express (PCIe)or NVM express (NVMe).

A plurality of memory systems 3B are individually attached to theconnectors 30 of the information processing device 2B and supported insuch an arrangement that they stand in an approximately verticaldirection. Using this structure, a plurality of memory systems 3B can bemounted collectively in a compact size, and the memory systems 3B can beminiaturized. Furthermore, the shape of each memory system 3B of thepresent embodiment is 2.5 inch small form factor (SFF). With this shape,the memory system 3B can be compatible with an enterprise HDD (eHDD) andthe easy system compatibility with the eHDD can be achieved.

Note that the memory system 3B is not limited to the use in anenterprise HDD. For example, the memory system 3B can be used as amemory medium of a consumer electronic device such as a notebookportable computer or a tablet terminal.

As can be understood from the above, the information processing system1B and the storage system 100 having the structure of the presentembodiment can achieve a mass storage advantage with the same advantagesof the first and second embodiments.

While certain embodiments have been described, these embodiments havebeen presented by way of example only, and are not intended to limit thescope of the inventions. Indeed, the novel embodiments described hereinmay be embodied in a variety of other forms; furthermore, variousomissions, substitutions and changes in the form of the embodimentsdescribed herein may be made without departing from the spirit of theinventions. The accompanying claims and their equivalents are intendedto cover such forms or modifications as would fall within the scope andspirit of the inventions.

What is claimed is:
 1. A storage device comprising: a nonvolatilememory; and a controller electrically connected to the nonvolatilememory and configured to: according to a first command received from ahost, the first command designating a first namespace and a firstcapacity, increase an over-provisioning capacity of the first namespaceby the designated first capacity.
 2. The storage device according toclaim 1, wherein the first namespace has a second capacity for storinguser data.
 3. The storage device according to claim 2, wherein acapacity allocated to the first namespace for storing the user data isthe second capacity after the over-provisioning capacity of the firstnamespace is increased.
 4. The storage device according to claim 1,further comprising a volatile memory, wherein the over-provisioningcapacity is allocated in the volatile memory.
 5. The storage deviceaccording to claim 1, wherein the nonvolatile memory includes aplurality of blocks, and the controller is further configured to:execute a garbage collection; and in executing the garbage collection,change a namespace to which an empty block belongs to another namespace,the empty block storing no valid data.
 6. The storage device accordingto claim 1, wherein the first command is a command with which no userdata is transmitted to the storage device.
 7. The storage deviceaccording to claim 1, wherein the first namespace includes a pluralityof groups, the plurality of groups each have a write frequency that is afrequency of storing user data, the write frequency of the plurality ofgroups being different from each other.
 8. The storage device accordingto claim 7, wherein the plurality of groups include a first group and asecond group, the write frequency of the first group being higher thanthe write frequency of the second group.
 9. The storage device accordingto claim 8, wherein the first namespace is one of a plurality ofnamespaces, the plurality of namespaces each have the plurality ofgroups, the first group is allocated across the plurality of namespaces.10. The storage device according to claim 1, wherein the controller isfurther configured to: according to increasing the over-provisioningcapacity of the first namespace, transmit an identifier and a size ofthe first namespace to the host.
 11. A method of controlling a storagedevice, the storage device including a nonvolatile memory, the methodcomprising: receiving a first command from a host, the first commanddesignating a first namespace and a first capacity; and according to thefirst command, increasing an over-provisioning capacity of the firstnamespace by the designated first capacity.
 12. The method according toclaim 11, wherein the first namespace has a second capacity for storinguser data.
 13. The method according to claim 12, wherein a capacityallocated to the first namespace for storing the user data is the secondcapacity after the over-provisioning capacity of the first namespace isincreased.
 14. The method according to claim 11, the storage devicefurther including a volatile memory, wherein the over-provisioningcapacity is allocated in the volatile memory.
 15. The method accordingto claim 11, wherein the nonvolatile memory includes a plurality ofblocks, and the method further comprises: executing a garbagecollection, and in executing the garbage collection, changing anamespace to which an empty block belongs to another namespace, theempty block storing no valid data.
 16. The method according to claim 11,wherein the first command is a command with which no user data istransmitted to the storage device.
 17. The method according to claim 11,wherein the first namespace includes a plurality of groups, theplurality of groups each have a write frequency that is a frequency ofstoring user data, the write frequency of the plurality of groups beingdifferent from each other.
 18. The method according to claim 17, whereinthe plurality of groups include a first group and a second group, thewrite frequency of the first group being higher than the write frequencyof the second group.
 19. The method according to claim 18, wherein thefirst namespace is one of a plurality of namespaces, the plurality ofnamespaces each have the plurality of groups, the first group isallocated across the plurality of namespaces.
 20. The method accordingto claim 11, further comprising: according to increasing theover-provisioning capacity of the first namespace, transmitting anidentifier and a size of the first namespace to the host.